System and Method for Multilane Link Rate Negotiation

ABSTRACT

A system and method are provided for negotiating a link data rate in a communication system using a plurality of data rates. In a system including a first device network-connected to a second device, auto-negotiation (AN) messages are mutually transmitted. The AN messages indicate rate information such as preferred data rate capabilities, if the device has a dual-rate capability, single data rate capabilities, or is capable of communicating over a plurality of physical medium lanes. If the AN messages are mutually transmitted, a negotiated link data rate is established. However, if one of the devices cannot send AN messages, the other device times-out, and a link data rate is established at the data rate transmitted by the device that is not AN-capable.

RELATED APPLICATIONS

This application is a continuation-in-part of a pending application entitled, SYSTEM AND METHOD FOR LINK RATE NEGOTIATION, invented by Brown et al., Ser. No. 12/236,918, filed Sep. 24, 2008, 2008, attorney docket no. applied_(—)285, which is incorporated herein by reference.

BACKGROUND OF THE INVENTION

1. Field of the Invention

This invention generally relates to communication systems and, more particularly, to a system and method for negotiating a link rate in a communication system where link partners are optionally capable of transceiving at two or more data rates, on one or more physical medium lanes.

2. Description of the Related Art

FIG. 1 is an auto-negotiation and training state diagram for an IEEE 802.3ap compliant network (prior art). The diagram is a state machine demonstrating the steps in an auto-negotiation (AN) process between boards across a backplane. Devices in such a backplane may be capable of operating at 1 gigabits per second (1 G), 10 G, and both 1 G and 10 G. Further, some units are able to send AN pages, compliant with Clause 73 of 802.3ap, to negotiate a data rate. Following power-up, reset, link fault, or time-out (100) the driver is disabled for a pre-determined period of time, which forces the link partner to restart. Next, the driver sends AN pages and the receiver looks for AN pages (102). If AN pages are detected, then the rate is negotiated based on local and received abilities.

If AN pages are not detected, then the Rx looks for a 1 G signal (104). If a 1 G signal is detected or negotiated, then the data path is configured for 1 G and 1 G acquisition begins (106). If 1 G cannot be detected, the receiver looks for a 10 G signal. If 10 G is negotiated, then the data path is configured for 10 G training and 10 G training begins (110). When 1 G acquisition or 10 G training is complete, the data path is configured for 1 G or 10 G, tracking and data transmission may begin at steps 108 and 112, respectively. If 10 G training does not complete within 500 ms, or if 1 G acquisition does not complete within 50 ms, or if a fault is detected while training, tracking, or acquiring, AN will restart (100).

Devices in a backplane may also be connected through more than one physical medium lane. As used herein, a physical medium lane is a physical medium, such as a cable or optical fiber. In some aspects, the link between two devices may be composed on multiple lanes. As an example, XAUI is a four-lane interface with a 3.125 Gbps baud rate or 2.5 Gbps data rate per lane with an aggregate data rate of 10 Gbps. For various reasons, such as backward compatibility or to manage power consumption, it may be necessary or desirable to operate at either the maximum rate of 10 Gbps, or a lower rate of 1 Gbps. For example, on a conventional XAUI backplane interface, it is common to have option of 1 Gbps on lane 0, with other lanes disabled when 1 Gbps rate is desired. In order for the links to run at a common rate, a common negotiation method is required.

It would be advantageous if a streamlined process of AN were developed that could account for devices capable of AN, dual-rate devices without AN capacity, single-rate devices, and multilane devices.

SUMMARY OF THE INVENTION

Disclosed herein are a system and method that permits physical layer devices (PHY) to negotiate rates over copper cable or optical links. With a compliant link partner, a rate can be selected at one end to match throughput requirements. The 1 G is more power conservative, and is useful when network throughput requirement are low. However, the 10 G is desirable when high throughput is required. The disclosed system automatically links partners with different link preferences, even if the link partners do not have an AN capability. Optionally, training for 10 G links may be supported to optimize performance, especially with highly dispersive, high loss cables.

As is conventional, AN pages are sent to, and received by compliant link partners. Through these AN pages the rate and, potentially, other features such as FEC and pause control may be negotiated. By enabling 1 G rate and disabling 10 G rate, the link rate may be configured to be 1 G from either end. By enabling both 1 G and 10 G rate, the link partner may control the link rate. With a non-compliant fixed rate link partner, the fixed rate is detected and the data path is appropriately configured. If a 10 G signal is detected, the data path is configured for 10 G, using either a single physical lane, or four 2.5 G lanes. If a 1 G signal is detected, the data path is configured for 1 G.

Accordingly, a method is provided for negotiating a link data rate in a communication system using a plurality of data rates. In a system including a first device network-connected to a second device, auto-negotiation (AN) messages are mutually transmitted. The AN messages indicate rate information such as preferred data rate capabilities, if the device has a dual-rate capability or a single data rate capabilities, and if a data rate capability is based upon the use of a single physical medium lane or a plurality of physical medium lanes. If the AN messages are mutually transmitted, a negotiated link data rate is established. However, if one of the devices cannot send AN messages, the other device times-out, and a link data rate is established at the data rate transmitted by the device that is not AN-capable.

If only one of the devices is capable of transmitting at two data rates, a link data rate is established at a data rate common to both devices. If both of the devices are capable of transmitting at two data rates and the devices have different preferred data rates, a link data rate is established at a system default preferred data rate.

Additional details of the above-described method and, a system for negotiating a link data rate in a communication system using a plurality of data rates, are provided below.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is an auto-negotiation and training state diagram for an IEEE 802.3ap compliant network (prior art).

FIG. 2 is a schematic block diagram of a system for negotiating a link data rate in a communication network using a plurality of data rates.

FIG. 3 is a state diagram for a universal auto-negotiation network with fixed or inferred Tx tap settings.

FIG. 4 is a state diagram for a universal auto-negotiation network with Tx tap training based upon IEEE 802.3 Clause 72.

FIG. 5 is a state diagram for a universal auto-negotiation network without AN signals.

FIG. 6 is a table summarizing exemplary rate negotiation criteria.

FIG. 7 is a table illustrating an example of how the negotiated rate may be indicated using the negotiated rate bits in the Backplane Ethernet Status register (7.48) (prior art).

FIG. 8 is a table summarizing the expected negotiated rate, based on the criteria set at each PHY, along with the actual negotiated rate result.

FIG. 9 is a flowchart illustrating a method for negotiating a link data rate in a communication system using a plurality of data rates.

DETAILED DESCRIPTION

FIG. 2 is a schematic block diagram of a system for negotiating a link data rate in a communication network using a plurality of data rates. The system 200 comprises a first device 202 with a transceiver 204 interfaced to a rate negotiation module 206 on line 208. A second device 210 has a transceiver 212, interfaced to a rate negotiation module 214 on line 216, and is network-connected to the first device transceiver on line 218. The rate negotiation module (RNM) 206 of the first device 202 and the RNM 214 of rate second device 210 mutually order the transmission of predetermined inquiry signals in the event that a negotiated data rate has not been determined.

In one scenario, the first device 202 transmits the inquiry signal at a first data rate and the second device transmits the inquiry signal at a second data rate. The first and second data rates may be data rates associated with a single physical medium lane 218 a, or a plurality of physical medium lanes, 218 b through 218 n, where n is a variable not limited to any particular value. There are two typical results for this scenario. In one result, the first and second device rate negotiation modules 206/214 order the transmission of non-predetermined data at the second data rate—if the second device receives an acknowledgement signal from the first device at the second data rate. Otherwise, the first and second device rate negotiation modules 206/214 order the transmission of non-predetermined data at the first data rate in the event of the first device receives an acknowledgement signal from the second device at the first data rate. In the event that the devices have single-rate capabilities at different frequencies, communication is not possible. Other circumstances where neither the first nor second device receives a response at the expected data rate are presented below.

In one aspect, non-predetermined Ethernet data at a first data rate may be transmitted at 10 gigabit per second (10 G) via a single physical medium lane 218 a, or over 4 physical medium lanes 218 b, 218 c, 218 d, and 218 n. Alternately, non-predetermined Ethernet data is transmitted at a second data rate of 1 G. It should be understood that the actual data rates may be higher than 1 G and 10 G due to line coding, e.g., 8B/10B for 1 G and 64B/66B for 10 G. It should also be understood however, that the system is not necessarily limited to any particular message protocol or data rate.

For example, if 4 lanes are transmitting non-predetermined Ethernet data at 2.5 G and 8B/10B is used, the actual data rate of each line is 3.125 G. As used herein, non-predetermined data is the actual information being communicated (data or control), not the redundant information accompanying the communications used for signal conditioning, dc balancing, or error correction. In another aspect, Ethernet data transmitted on a single physical lane at the 10 G rate may be in a protocol such as 10 Gps (i.e. Roman numeral X) Attachment Unit Interface (XAUI), 10GBASE-KX4, or 10GBASE-LX4.

In one aspect, the first device transceiver 204 includes a clock and data recovery (CDR) system 224, and the second device transceiver includes clock and data recovery system 226. The first and second device transceivers fail to receive an acknowledgement signal, or any other kind of transmission, if the CDR systems fail to lock to received signals. The device transceivers successfully receive acknowledgement signals in response to the CDR systems locking on to received signals.

In one aspect, the rate negotiation modules 206/214 of the first and second devices order the transmission of non-predetermined data at the first rate in response to the following circumstances—the second device is capable of transceiving at the first and second data rates, but the first device is only capable of transmitting (and receiving) at the first data rate. Since the second device does not receive an acknowledgement signal at the second data rate from the first device, the second device times-out, and after the time-out, transmits at the first data rate, in response to detecting a signal at the first data rate.

Likewise, if the first device is capable of transmitting at the first and second data rates, and the second device is only capable of transmitting at the second data rate, the rate negotiation modules 206/214 order the transmission of non-predetermined data at the second data rate in response to the first device timing-out after not receiving an acknowledgement signal at the first data rate from a second device, and then detecting signals at the second data rate.

In a second scenario, which typically occurs prior to the mutually transmission of inquiry signals described above in the first scenario, the rate negotiation module 206 of the first device, orders the transmission an AN message indicating rate information such as preferred data rate capabilities, if the first device has a dual-rate capability, or single data rate capabilities. The result of this scenario is that the rate negotiation modules 206/214 of the first and second devices mutually order the transmission of inquiry signals in response to the first device not receiving an AN message from the second device.

In an alternative result to the second scenario, the rate negotiation module of the first device times-out because an AN message has been received from the second device, and after the time-out, the first and second devices transmit at the second data rate.

In a third scenario, which typically occurs prior to mutually transmitting inquiry signals in the first scenario, the rate negotiation modules 206/214 of the first and second devices, mutually order the transmission of AN, which as mentioned above, indicating rate information such as preferred data rate capabilities and single data rate capabilities. In this scenario, the rate negotiation modules of each device unilaterally determine a common negotiated rate from evaluating their own data rate capabilities and received rate capabilities. Then, the first and second devices 202/210 mutually receive AN replies indicating a successful negotiation, and the rate negotiation modules 206/214 order the transmission of non-predetermined data at the negotiated data rate.

In one aspect, the first and second devices transmit AN messages in accordance with either an IEEE 802.3ap Clause 73 protocol or an 802.3 Clause 37 protocol, and further include a message indicating compatibility with a proprietary negotiation protocol. For example, the proprietary protocol may include all, or some of the elements of the system 200 described herein. Then, the first and second devices receive AN replies indicating compliance with the proprietary negotiation protocol.

In a fourth scenario, the first and second device transceivers 204/212 are capable of transceiving at both the first and second data rates. The first device rate negotiation module 206 has a control interface on line 220 for selecting the first data rate preference, and the second device rate negotiation module 214 has a control interface on line 222 for selecting the second data rate preference. The rate negotiation modules 206/214 of the first and second devices order the transmission of non-predetermined data at the second rate in response to the first device timing-out before the second device. Timing-out is defined as not receiving an expected transmission within a predetermined duration of time.

Because of the time-out, the preference of the second device becomes data rate that is used. Thus, the time-outs can be used to select a default data rate in the event of competing preferences. For example, a first time-out duration may be associated with the first data rate, and a second time-out duration associated with a system default rate, greater than the first time-out duration, may be associated with the second data rate. In one aspect, the default data rate is a system default rate, and the first and second durations are system-wide values that are shared in common by all the link partners.

In the fourth scenario, the rate negotiation modules 206/214 of the first and second devices order the transmission of non-predetermined data at the second rate in response to the first device timing-out before the second device.

In a fifth scenario, the first device 202 disables further transmissions for a predetermined period of time in response to a device reset or management intervention message received at the control interface on line 220. As a result, the rate negotiation module 214 of the second device orders the restarting and disabling transmissions for a pre-determined duration of time in response to the lack of received transmissions from the first device. Then, the rate negotiation modules 206/214 mutually order the transmission of inquiry signals, following the restart, if a negotiated data rate has not been determined.

The RNMs 206 and 214 may be enabled in hardware using logic circuitry or programmable gate arrays. The RNMs may also be enabled as processor software instructions stored as an application in memory (not shown), and executed by a processor (not shown). Alternately, the RNMs may be enabled as a combination of hardware and software.

Functional Description

FIG. 3 is a state diagram for a universal auto-negotiation network with fixed or inferred Tx tap settings. Following power-up, reset, link fault, or time-out (300) the driver is disabled for a predetermined period of time to force the link partner to restart. Next, the driver sends AN pages and the receiver looks for AN pages (302). If AN pages are detected, then the rate is negotiated based on local and received abilities. If AN pages are not detected, then the Rx looks for a 10 G signal (304). If a 10 G signal is not detected, then the Rx looks for a 1 G signal (306). The driver continues to send AN pages until a rate is determined or AN is restarted. In parallel with Step 304, if a 1 G signal is detected or negotiated (306), then the data paths are configured for 1 G and 1 G acquisition begins (308).

If a 10 G signal is detected or negotiated (304), then the data paths are configured for 10 G and 10 G acquisition begins (310). Note: the 10 G data path may consist of either a single physical lane, or 4 physical lanes at 2.5 G each lane. When 1 G or 10 G acquisition is complete, the data path is configured for 1 G or 10 G (312 and 314, respectively), and tracking and data transmission begins.

If 10 G acquisition does not complete within a predetermined period of time, or if 1 G acquisition does not complete within a predetermined period of time, or if a fault is detected while tracking or acquiring, AN starts all over again (300).

FIG. 4 is a state diagram for a universal auto-negotiation network with Tx tap training based upon IEEE 802.3 Clause 72. This state machine demonstrates the steps involved when Tx training is required. Following power-up, reset, link fault, or time-out (400) the driver is disabled for a predetermined period of time to force the link partner to restart. Next, the driver sends AN pages and the receiver looks for AN pages (402). If AN pages are detected, then the rate is negotiated based on local and received abilities. If AN pages are not detected, then the Rx looks for a 10 G signal in the 10GBASE-R format (404). If a 10 G signal is not detected, then the Rx looks for a 1 G signal in 8B/10B format (406). If the 10 G rate is negotiated, then the data path, using one or more physical lanes, is configured for 10 G training, and 10 G training begins (410). If a 10 G signal is detected, then the data path is configured for 10 G and 10 G acquisition begins (416). If a 1 G signal is detected or negotiated, then the data path is configured for 1 G and 1 G acquisition begins (408).

When 1 G acquisition (408) is complete, the data path is configured for 1 G tracking (412) and data transmission may begin. When 10 G acquisition (416) or 10 G training (410) is complete, the data path is configured for 10 G tracking (414) and data transmission may begin.

If 10 G training (410) does not complete within a predetermined period of time, if 10 G acquisition (416) does not complete within a predetermined period of time, if 1 G acquisition (408) does not complete within a predetermined period of time, or if a fault is detected while training, tracking, or acquiring, AN will start all over again (400). If 10 G training is not supported, the process goes from Step 404 to 10 G acquisition (416), as in FIG. 3.

It is possible to negotiate a link rate without the need for Clause 73 AN pages. The system permits rate negotiation without the need for the extra complexity of supporting AN pages and its associated state machine. The system is appropriate for both direct attach copper cables and optical modules, and more amenable to transceivers without the built-in capability to send or receive AN pages. One disadvantage of not using AN pages is that the capability is given up for negotiating functions not related to signal rate and format.

FIG. 5 is a state diagram for a universal auto-negotiation network without AN signals. This state machine demonstrates the steps involved in rate negotiation for SFP+ copper cable or optical applications without special negotiation signals (e.g., Clause 73 AN). Following power-up, reset, or link fault the process is restarted 500. Optionally, the Tx driver is disabled for a predetermined period of time. This restart synchronizes both transceivers to the beginning of the negotiation process. This step is not always required, but is nevertheless a good way to align the timers and maximize timing margins and/or reduce wait times. After restart, if 10 G is preferred, the Tx output is enabled sending a valid 10 G 64B/66B signal (502). If a 10 G signal is detected (504) within time T1, then 10 G acquisition begins (506), followed by 10 G tracking (508). Otherwise an attempt is made to detect a 1 G signal (512). As noted above, the 10 G signal may be transmitted via one or more physical lanes.

After restart (500), if 1 G is preferred, the Tx output is enabled sending a valid 8B/10B signal (510). If a 1 G signal is detected within time T2, then 1 G acquisition begins (514), followed by 1 G tracking (516). Otherwise, an attempt is made to detect a 10 G signal (504).

If 10 G acquisition (506) does not complete within a predetermined period of time, or 1 G acquisition (514) does not complete within a predetermined period of time, or if a fault is detected while tracking or acquiring, the state machine restarts (500).

By setting T2 sufficiently larger than T1, simultaneous preference for 1 G and 10 G will resolve to 1 G at both ends, since the end that prefers 10 G will go (first) to the 1 G detect mode. Conversely, by setting T1 sufficiently larger than T2, simultaneous preference for 1 G and 10 G will resolve to 10 G at both ends, since the end that prefers 1 G will go (first) to the 10 G detect mode.

FIG. 6 is a table summarizing exemplary rate negotiation criteria. In one aspect (not shown), the three technology ability bits from Clause 73 may be re-defined to indicate the desired criteria. For example, A0 and A9 may indicate ability to support 1 G and 10 G, respectively. Then, A1 can be used to indicate preference for 1 G (1) or 10 G (0). Alternately, the bit positions and values may be assigned different meanings. An example of how bits A0, A1, and A2 may be used to indicate supported rates and preferences as shown in the table.

Note that any 3 bits may be employed to indicate the above supported rate scenarios.

FIG. 7 is a table illustrating an example of how the negotiated rate may be indicated using the negotiated rate bits in the Backplane Ethernet Status register (7.48) (prior art). Bits 3:1 may be used as follows:

-   -   000b: link rate not negotiated;     -   100b: link negotiated to 10 G; and,     -   001b: link negotiated to 1 G.

Note that this definition is consistent with prior art 802.3ap Clause 72 and that alternatively any two bits may be used to indicate the negotiated status.

FIG. 8 is a table summarizing the expected negotiated rate, based on the criteria set at each PHY, along with the actual negotiated rate result.

FIG. 9 is a flowchart illustrating a method for negotiating a link data rate in a communication system using a plurality of data rates. Although the method is depicted as a sequence of numbered steps for clarity, the numbering does not necessarily dictate the order of the steps. It should be understood that some of these steps may be skipped, performed in parallel, or performed without the requirement of maintaining a strict order of sequence. The method starts at Step 900.

In a system including a first device network-connected to a second device, Step 904 mutually generate waveforms representing predetermined inquiry signals in the event that a negotiated data rate has not been determined. The first device transmits the inquiry signal at a first data rate and the second device transmits the inquiry signal at a second data rate. The first and second data rates are the data rates associated with a single physical medium lane or the resultant data rate associated with a plurality of physical medium lanes. In the event of the second device receives an acknowledgement signal at the second data rate, the first and second devices transmit non-predetermined data at the second data rate in Step 906. In the event of the first device receives an acknowledgement signal at the first data rate, the first and second devices transmit non-predetermined data at the first data rate in Step 908. In one aspect, non-predetermined Ethernet data is transmitted at a first data rate of 10 G via a single physical medium lane at 10 G, or 4 physical medium lanes at 2.5 G per lane. Alternately, non-predetermined Ethernet data is transmitted at a second date rate of 1 G. In another aspect, non-predetermined Ethernet data is transmitted on 4 physical medium lanes as 8B/10B coded information, at 3.125G per lane. The Ethernet 10 G data may be in a XAUI, 10GBASE-KX4, or 10GBASE-LX4 format.

In one aspect, prior to mutually transmitting inquiry signals in Step 904, the first device transmits an AN message in Step 902 a. The AN message indicates rate information such as preferred data rate capabilities and single data rate capabilities. Then, mutually transmitting inquiry signals in Step 904 includes mutually transmitting inquiry signals in response to the first device not receiving an AN message from the second device. As an alternative, the first and second devices transmit non-predetermined data at the second rate (Step 906) because the first device receives inquiry signals at the second data rate from the second device. Then, the first device times-out, and the first device transmits at the second data rate.

In another aspect, Step 901 a programs the first device, which is capable of transmitting at the first and second data rates, with a first data rate preference. Step 901 b programs the second device, which is also capable of transmitting at the first and second data rate, with a second data rate preference. Then, mutually transmitting predetermined inquiry signals in Step 904 includes the first device transmitting the inquiry signal at the first data rate, and the second device transmitting the inquiry signal at a second data rate. In Step 906 the first and second devices transmit non-predetermined data at the second rate in response to the first device timing-out before the second device, where timing-out is defined as not receiving an expected transmission within a predetermined duration of time.

In another aspect, a first time-out duration is associated with the first data rate, and a system default second time-out duration, greater than the first time-out duration, is associated with the second data rate. Then, mutually transmitting predetermined inquiry signals in Step 904 includes the first device transmitting the inquiry signal at the first data rate, and the second device transmitting the inquiry signal at a second data rate. The first and second devices transmit non-predetermined data at the second rate (Step 906) in response to the first device timing-out before the second device.

In another variation the first and second devices transmitting non-predetermined data at the first data rate (Step 908) includes the second device being capable of transmitting at the first and second data rates, but not receiving an acknowledgement signal at the second data rate from a first device only capable of transmitting at the first data rate. In this circumstance, the second device times-out and begins transmissions at the first rate. Otherwise, the first and second devices may transmit non-predetermined data at the second data rate (Step 908) because the first device, capable of transmitting at the first and second data rates, does not receive an acknowledgement signal at the first data rate from a second device, as the second device is only capable of transmitting at the second data rate. In this circumstance, the first device times-out and begins transmissions at the second data rate.

In another aspect, in Step 901 c the first device disables further transmissions for a predetermined period of time in response to a device reset or management intervention. In response to the lack of received transmissions, the second device restarts and disables transmissions for a pre-determined duration of time in Step 901 d. Following the restart, the first and second devices mutually transmit inquiry signals (Step 904) if a negotiated data rate has not been determined (Step 902 c and 902 d).

In a different aspect, Step 902 b mutually transmits AN messages indicating rate information such as preferred data rate capabilities and single rate capabilities, prior to mutually transmitting inquiry signals (Step 904). In Step 902 c, each device unilaterally determines a common negotiated data rate in response to evaluating their own data rate capabilities and received rate capabilities. Step 902 d mutually receives AN replies indicating a successful negotiation. Then, transmitting non-predetermined data between the first and second devices in Step 906 or 908 includes transmitting non-predetermined data at the negotiated data rate.

In one aspect, transmitting the AN messages in Step 902 b includes transmitting an AN message in accordance with either an IEEE 802.3ap Clause 73 protocol or an 802.3 Clause 37 protocol, with a message indicating compatibility with a proprietary negotiation protocol. Then, receiving AN replies in Step 902 d includes receiving a message indicating compliance with the proprietary negotiation protocol. For example, the proprietary protocol may include all, or some of the steps presented in the explanation of FIG. 9.

The first and second devices not receiving an acknowledgement signals in Step 906 and 908 may be a result of CDR systems in the devices failing to lock to received signals. Likewise, first and second devices transmitting non-predetermined data may be a result of the CDR systems in the first and second devices locking to received signals.

A system and method for negotiating a link data rate have been provided. Examples, of particular circuitry and process flows have been given to illustrate the invention. However, the invention is not limited to merely these examples. Likewise, examples have been given in the context of an Ethernet protocol and particular data rates. Again the invention is not limited to these examples. Other variations and embodiments of the invention will occur to those skilled in the art. 

1. In a communication system using a plurality of data rates, a method for negotiating a link data rate between network-connected devices, the method comprising: in a communication system including a first device network-connected to a second device, mutually generating energy waveforms representing predetermined inquiry signals transmitted in the event that a negotiated data rate has not been determined, with the first device transmitting the inquiry signal at a first data rate and the second device transmitting the inquiry signal at a second data rate, where the first and second data rates are selected from a group consisting of a data rate associated with a single physical medium lane and the resultant data rate associated with combining a plurality of physical medium lanes; in the event of the second device receiving an energy waveform representing an acknowledgement signal at the second data rate, the first and second devices generating energy waveforms representing non-predetermined data transmitted at the second data rate; and, in the event of the first device receiving an energy waveform representing an acknowledgement signal at the first data rate, the first and second devices generating energy waveforms representing non-predetermined data transmitted at the first data rate.
 2. The method of claim 1 wherein the first and second devices transmitting non-predetermined data at the first data rate includes first and second devices transmitting non-predetermined Ethernet data at a 10 gigabit per second (10 G) data rate via an interface selected from a group consisting of a single physical medium lane at 10 G and 4 physical medium lanes, at 2.5 G per lane; and, wherein the first and second devices transmitting non-predetermined data at the second data rate includes first and second devices transmitting non-predetermined Ethernet data at a 1 gigabit per second (1 G) data rate.
 3. The method of claim 2 wherein first and second devices transmitting non-predetermined Ethernet data on 4 physical medium lanes at 2.5 G per lane includes transmitting 8B/10B coded information on 4 physical lanes, at 3.125 G per lane.
 4. The method of claim 2 wherein first and second devices transmitting non-predetermined Ethernet data at the 10 G data rate includes transmitting on a single medium physical lane using a protocol selected from a group consisting of 10 Gps Attachment Unit Interface (XAUI), 10 GBASE-KX4, and 10GBASE-LX4.
 5. The method of claim 1 further comprising: prior to mutually transmitting inquiry signals, the first device transmitting an AN message indicating rate information selected from a group consisting of preferred data rate capabilities and single data rate capabilities; and, wherein mutually transmitting inquiry signals includes mutually transmitting inquiry signals in response to the first device not receiving an AN message from the second device.
 6. The method of claim 1 further comprising: programming the first device, capable of transmitting at the first and second data rates, with a first data rate preference; programming the second device, capable of transmitting at the first and second data rate, with a second data rate preference; wherein mutually transmitting predetermined inquiry signals includes the first device transmitting the inquiry signal at the first data rate, and the second device transmitting the inquiry signal at a second data rate; and, wherein the first and second devices transmitting non-predetermined data at the second rate includes the first and second devices transmitting non-predetermined data at the second rate in response to the first device timing-out before the second device, where timing-out is defined as not receiving an expected transmission within a predetermined duration of time.
 7. The method of claim 6 wherein a first time-out duration is associated with the first data rate, and a system default second time-out duration, greater than the first time-out duration, is associated with the second data rate; wherein mutually transmitting predetermined inquiry signals includes the first device transmitting the inquiry signal at the first data rate, and the second device transmitting the inquiry signal at a second data rate; and, wherein the first and second devices transmitting non-predetermined data at the second rate includes the first and second devices transmitting at the second data rate in response to the first device timing-out before the second device.
 8. The method of claim 1 wherein the first and second devices transmitting non-predetermined data at the first data rate includes a second device, capable of transmitting at the first and second data rates, not receiving an acknowledgement signal at the second data rate from a first device only capable of transmitting at the first data rate, and the second device timing-out; and, wherein the first and second devices transmitting non-predetermined data at the second data rate includes a first device, capable of transmitting at the first and second data rates, not receiving an acknowledgement signal at the first data rate from a second device only capable of transmitting at the second data rate, and the first device timing-out.
 9. The method of claim 1 further comprising: in response to a condition selected from a group consisting of a device reset and a management intervention, the first device disabling further transmissions for a predetermined period of time; in response to the lack of received transmissions, the second device restarting and disabling transmissions for a pre-determined duration of time; and, following the restart, the first and second devices mutually transmitting inquiry signals if a negotiated data rate has not been determined.
 10. The method of claim 1 further comprising: prior to mutually transmitting inquiry signals, mutually transmitting AN messages indicating rate information selected from a group consisting of preferred data rate capabilities and single data rate capabilities; each device unilaterally determining a common negotiated data rate in response to evaluating their own data rate capabilities and received rate capabilities; mutually receiving AN replies indicating a successful negotiation; and, wherein transmitting non-predetermined data between the first and second devices includes transmitting non-predetermined data at the negotiated data rate.
 11. In a communication network using a plurality of data rates, a system for negotiating a link data rate, the system comprising: a first device with a transceiver interfaced to a rate negotiation module; a second device with a transceiver interfaced to a rate negotiation module and network-connected to the first device transceiver; wherein the rate negotiation modules of the first and second devices mutually order the transmission of predetermined inquiry signals in the event that a negotiated data rate has not been determined, with the first device transmitting the inquiry signal at a first data rate and the second device transmitting the inquiry signal at a second data rate, where the first and second data rates are selected from a group consisting of a data rate associated with a single physical medium lane and the resultant data rate associated with combining a plurality of physical medium lanes; wherein the first and second device rate negotiation modules order the transmission of non-predetermined data at the second data rate if the second device receives an acknowledgement signal from the first device at the second data rate; and, wherein the first and second device rate negotiation modules order the transmission of non-predetermined data at the first data rate in the event of the first device receives an acknowledgement signal from the second device at the first data rate.
 12. The system of claim 11 wherein the first and second devices transmit non-predetermined Ethernet data at a first data rate of 10 gigabit per second (10 G) via an interface selected from a group consisting of a single physical medium lane at 10 G and 4 physical medium lanes, at 2.5 G per lane, and non-predetermined Ethernet data at a second data rate of 1 G.
 13. The system of claim 12 wherein first and second devices transmit non-predetermined Ethernet data on 4 physical medium lanes at 2.5 G per lane includes transmitting 8B/10B coded information on 4 physical lanes, at 3.125 G per lane.
 14. The system of claim 12 wherein first and second devices transmit Ethernet data at the 10 G data rate on a single physical medium lane using a protocol selected from a group consisting of 10 Gps Attachment Unit Interface (XAUI), 10GBASE-KX4, and 10GBASE-LX4.
 15. The system of claim 11 wherein the rate negotiation module of the first device, prior to the mutually transmission of inquiry signals, orders the transmission an auto-negotiation (AN) message indicating rate information selected from a group consisting of preferred data rate capabilities and single data rate capabilities; and, wherein the rate negotiation modules of the first and second devices mutually order the transmission of inquiry signals in response to the first device not receiving an AN message from the second device.
 16. The system of claim 11 wherein the first and second device transceivers are capable of transceiving at both the first and second data rates; wherein the first device rate negotiation module has a control interface for selecting the first data rate preference; wherein the second device rate negotiation module has a control interface for selecting the second data rate preference; wherein the rate negotiation modules of the first and second devices order the transmission of non-predetermined data at the second rate in response to the first device timing-out before the second device, where timing-out is defined as not receiving an expected transmission within a predetermined duration of time.
 17. The system of claim 16 wherein a first time-out duration is associated with the first data rate, and a system default second time-out duration, greater than the first time-out duration, is associated with the second data rate; and, wherein the rate negotiation modules of the first and second devices order the transmission of non-predetermined data at the second rate in response to the first device timing-out before the second device.
 18. The system of claim 11 wherein the rate negotiation modules of the first and second devices order the transmission of non-predetermined data at the first rate in response to a second device, capable of transceiving at the first and second data rates, not receiving an acknowledgement signal at the second data rate from a first device only capable of transmitting at the first data rate, and the second device timing-out; and, wherein the rate negotiation modules of the first and second devices order the transmission of non-predetermined data at the second data rate in response to the first device, capable of transmitting at the first and second data rates, not receiving an acknowledgement signal at the first data rate from a second device only capable of transmitting at the second data rate, and the first device timing-out.
 19. The system of claim 11 wherein the first device disables further transmissions for a predetermined period of time in response to a condition selected from a group consisting of a device reset and a management intervention message received at a control interface; wherein the rate negotiation module of the second device orders the restarting and disabling transmissions for a pre-determined duration of time in response to the lack of received transmissions from the first device; and, wherein the rate negotiation modules of the first and second devices mutually order the transmission of inquiry signals, following the restart, if a negotiated data rate has not been determined.
 20. The system of claim 11 wherein the rate negotiation modules of the first and second devices, prior to mutually transmitting inquiry signals, mutually order the transmission of AN messages indicating rate information selected from a group consisting of preferred data rate capabilities and single data rate capabilities; wherein the rate negotiation modules of each device unilaterally determine a common negotiated rate from evaluating their own data rate capabilities and received rate capabilities; wherein first and second devices mutually receive AN replies indicating a successful negotiation, and the rate negotiation modules order the transmission of non-predetermined data at the negotiated data rate. 